Conversation
|
+1 |
|
@cgruber Any news on this PR? |
|
Sorry, have been overloaded this quarter. I'll try to get this done in the next few days. I need to take this into google's internal repo and then push it out and I'm OOO tomorrow. Might get to it tonight, but if not, later this week. |
|
Context question... do you mean 22.0-SNAPSHOT, or do you mean 22? Do you need unreleased functionality, or does 22.0 resolve the cygwin issue? |
|
I don't remember why I used 22.0-SNAPSHOT, but I'm sure there has been a reason. I will find out again why I didn't use 22.0 and let you know. |
|
It's possible that when you filed the pull request, 22.0 was not yet
released. But let me know if you need post-22 functionality.
…On Tue, 27 Jun 2017 at 18:49 Yannic Bonenberger ***@***.***> wrote:
I don't remember why I used 22.0-SNAPSHOT, but I'm sure there has been a
reason. I will find out again why I didn't use 22.0 and let you know.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#39 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAUN4oo9pBENjjKkE6elW9Zf3xgqBAVgks5sIbE4gaJpZM4M6jbE>
.
|
|
The reason I uses 22.0-SNAPSHOT was that 22.0 has not been released in April. I updated this PR to use 22.0 |
|
Other snapshot dependencies were removed/updated in #41 because it led to runtime failures |
|
Hello |
5 participants
Fixes failing build